-
Notifications
You must be signed in to change notification settings - Fork 13
chore(GHA): Run Java CI testing for MPL Latest Release #1605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
uses: ./.github/workflows/dafny-interop.yml | ||
with: | ||
mpl-dafny: ${{needs.getLatestReleaseMplVersion.outputs.version}} | ||
mpl-commit: ${{needs.getMplDafnyVersion.outputs.dafnyVersion}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this doesn't make sense, why for the mpl commit are we supplying the dafny version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the MPL version will be built with its own Dafny version, and we pick this up from the project properties file of the MPL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look at the first input to dafny-interop.yml.
workflow_dispatch: # allows triggering this manually through the Actions UI | ||
# TODO: Remove this before merging to main. We don't want this workflow running in CI | ||
# on PRs because we expect it to fail when the MPL is actually updated since the last version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a flag which by default is on, and if off, doesn't run 105-113 (Test Vectors) but runs the examples. Needed so that if TVs fail, we're still able to test examples.
## [3.8.1](v3.8.0...v3.8.1) (2025-04-01) ### Fixes * return plaintext items in UnprocessedItems in BatchWriteIttem ([#1642](#1642)) ([7c7c8a1](7c7c8a1)) ### Maintenance * add Rust generated test vectors ([#1638](#1638)) ([a285eac](a285eac)) * bump mpl and smithy-dafny ([#1762](#1762)) ([8179af4](8179af4)) * **dafny:** let FileIO deal in uint8 rather than bv8 ([#1746](#1746)) ([428a013](428a013)) * **deps:** bump actions/setup-java from 3 to 4 in /.github/workflows ([#1367](#1367)) ([f04bc40](f04bc40)) * **deps:** bump actions/setup-java from 3 to 4 in /.github/workflows ([#1654](#1654)) ([ddb69e1](ddb69e1)) * **deps:** bump org.junit.jupiter:junit-jupiter-api ([#1656](#1656)) ([d988c6e](d988c6e)) * **deps:** bump org.junit.jupiter:junit-jupiter-engine ([#1650](#1650)) ([4f18689](4f18689)) * **deps:** bump software.amazon.awssdk:bom ([#1643](#1643)) ([4c41746](4c41746)) * **deps:** bump software.amazon.awssdk:bom ([#1644](#1644)) ([84e2c56](84e2c56)) * **deps:** bump software.amazon.awssdk:core ([#1645](#1645)) ([dec98d6](dec98d6)) * **GHA:** Run Java CI testing for MPL Latest Release ([#1605](#1605)) ([2eb36b3](2eb36b3)) * **java:** allow local testing v3.8.0 ([#1628](#1628)) ([119a42b](119a42b)) * **java:** update versions of lombok and aws-sdk-ddb ([#1646](#1646)) ([099014e](099014e)) * re-enable Dafny for MacOS ([#1738](#1738)) ([6f729c3](6f729c3)) * Remove Dafny warnings ([#1742](#1742)) ([4a9d617](4a9d617)) * **rust:** enable wrapped client test vectors ([#1648](#1648)) ([20fee58](20fee58))
* return plaintext items in UnprocessedItems in BatchWriteIttem ([#1642](#1642)) ([7c7c8a1](7c7c8a1)) * add Rust generated test vectors ([#1638](#1638)) ([a285eac](a285eac)) * bump mpl and smithy-dafny ([#1762](#1762)) ([8179af4](8179af4)) * **dafny:** let FileIO deal in uint8 rather than bv8 ([#1746](#1746)) ([428a013](428a013)) * **deps:** bump actions/setup-java from 3 to 4 in /.github/workflows ([#1367](#1367)) ([f04bc40](f04bc40)) * **deps:** bump actions/setup-java from 3 to 4 in /.github/workflows ([#1654](#1654)) ([ddb69e1](ddb69e1)) * **deps:** bump org.junit.jupiter:junit-jupiter-api ([#1656](#1656)) ([d988c6e](d988c6e)) * **deps:** bump org.junit.jupiter:junit-jupiter-engine ([#1650](#1650)) ([4f18689](4f18689)) * **deps:** bump software.amazon.awssdk:bom ([#1643](#1643)) ([4c41746](4c41746)) * **deps:** bump software.amazon.awssdk:bom ([#1644](#1644)) ([84e2c56](84e2c56)) * **deps:** bump software.amazon.awssdk:core ([#1645](#1645)) ([dec98d6](dec98d6)) * **GHA:** Run Java CI testing for MPL Latest Release ([#1605](#1605)) ([2eb36b3](2eb36b3)) * **java:** allow local testing v3.8.0 ([#1628](#1628)) ([119a42b](119a42b)) * **java:** update versions of lombok and aws-sdk-ddb ([#1646](#1646)) ([099014e](099014e)) * re-enable Dafny for MacOS ([#1738](#1738)) ([6f729c3](6f729c3)) * Remove Dafny warnings ([#1742](#1742)) ([4a9d617](4a9d617)) * **rust:** enable wrapped client test vectors ([#1648](#1648)) ([20fee58](20fee58))
Issue #, if available:
Description of changes:
Adds a daily job to check that the HEAD of DB-ESDK is compatible with the latest release of the MPL (pulled from Maven).
An important part is that this should be independent of Daily CI / Push CI / Pull CI, because when the MPL is actually updated, we will see errors with testing the last release, and we don't want our current CI process to get affected because of this.
We also won't need to go through the pain of running the MCM step to run dafny-interop.yml manually for the latest released version of the MPL. This new workflow does it automatically, and the oncall just needs to verify that everything is green.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.